Used "PC Tuneup" to repair and defrag registry, but no improvement.1 person needs an answerI do too

Hi HJFisher,Does the Windows Error Reporting window provide additional data (such as thefile name - dll moduleinvolved)? More details would help.

The Windows error reporting window does not mention other data besides Windows Explorer, but it does invite me to send a report to Microsoft. I have sent that report several times, but there is no followup. One other thing that seems to be connected with this behavior: About 30 seconds after the Windows Explorer error reporting window closes, another error reporting window appears and says that "Dr Watson debugging has encountered an error and needs to close." I don't know what "Dr Watson debugging" is. Is this information helpful?

Here is more information, obtained by clicking on "See what this report contains": AppName: explorer.exe AppVer: 6.0.2900.3156 ModName: shell32.dll ModVer: 6.0.2900.3402 offset: 00054ec1Hope this helps. Thanks for your assistance.

Hi HJFisher,Shell32.dll is a built-in module. I'd try the clean boot troubleshooting method to see if this error is caused by third-party programs/drivers.How to perform a clean boot procedure to determine whether background programs are interfering with a game or a program that you currently use: http://support.microsoft.com/kb/331796Ramesh Srinivasan, Microsoft MVP [Windows Desktop Experience]

This procedure will not work for me, sinceit requires me to clickthe Start button as the first step.BUT clicking the Start button is the very thing which brings up the error message and causes the computer to hang up. Can you suggest any other way of approaching the problem?